-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auto release on vnext #5426
auto release on vnext #5426
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: 176f5c6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
3472f03
to
93fa627
Compare
93fa627
to
ee582c6
Compare
ee582c6
to
7e1f3ec
Compare
run: echo "//registry.npmjs.org/:_authToken=${{ secrets.VNEXT_NPM_TOKEN }}" > .npmrc | ||
- name: Publish | ||
if: needs.changesetcheck.outputs.CHANGESETS == 'found' | ||
run: pnpm publish -r --no-git-checks --tag next --access public --dry-run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apply dry run for now
if: needs.changesetcheck.outputs.CHANGESETS == 'found' | ||
run: pnpm publish -r --no-git-checks --tag next --access public --dry-run | ||
env: | ||
NPM_CONFIG_PROVENANCE: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This gets us the provenance tag on npmjs.com
a47d5cd
to
b9e9d4f
Compare
b9e9d4f
to
a9b84ec
Compare
a9b84ec
to
73612dc
Compare
In prep for auto-releasing from v-next, switch the v-next packages to be named under the `@ignored` org. Set the versions to `v2.0.0` in prep for manual release.
Taking the `@ignored` changes and applying them across imports and things like the test commands.
Apply the prerelease config based on a flag of `next`.
2747c0d
to
0cb9e6b
Compare
0cb9e6b
to
9cac542
Compare
9cac542
to
b49e663
Compare
999caba
to
2606d81
Compare
2606d81
to
84da594
Compare
There are 3 moves here: - Remove the pushing of tags - Move the if check to the job level rather than per step - temporarily comment out the git push
84da594
to
2eab529
Compare
2eab529
to
a6395a1
Compare
a6395a1
to
a5a5a08
Compare
a5a5a08
to
176f5c6
Compare
Setup auto deployment of
v-next
packages.Approach
v-next
packages to be under the@ignored
org in npm@nomicfoundation/hardhat-core
->@ignored/hardhat-vnext-core
@nomicfoundation/hardhat-build-system
->@ignored/hardhat-vnext-build-system
@nomicfoundation/hardhat-errors
->@ignored/hardhat-vnext-errors
@nomicfoundation/hardhat-node-test-reporter
->@ignored/hardhat-vnext-node-test-reporter
@nomicfoundation/hardhat-utils
->@ignored/hardhat-vnext-utils
@nomicfoundation/hardhat-zod-utils
->@ignored/hardhat-vnext-zod-utils
@nomicfoundation/hardhat
->@ignored/hardhat-vnext
2.0.0
for each of these packages manuallyVNEXT_NPM_TOKEN
that is limited to thev-next
packagesv-next-changesets-release.yml
leveraging theVNEXT_NPM_TOKEN
v-next
package that has a major update to3.0.0-next.0
prereleasev-next
this PR should publish pre-release versions of eachv-next
package under safe@ignored
variants.